This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
~Lorraine Chuveluskietsi 2.Oct.08 09:12 AM a Web browser Sametime Standard8.0.1Windows
[sorry this post is going to be a bit long winded, but there's a lot of relevant info]
I am trying to upgrade to Sametime 8.0.1 and am having some problems with the buddy list.
The scenario is as follows:
Domino domain for approx 1,000 users. a number of mail servers, apps servers, an admin server and the Sametime server all exist in the same domain.
Most of the Domino servers have been upgraded to Domino 8.0.1.
The remaining Sametime server runs Sametime 6.5.1 on Domino 6.5.4. This Sametime server uses Domino for authentication.
The intention is to build a new Sametime server in a standalone domain, and have it look up to the Admin server via Domino LDAP to authenticate users.
Everything has gone fine, but I am now up to the point where users buddy lists need to be migrated to the new server, and this is where things are falling down.
My first tests have been with the sandbox tool for converting names to LDAP, but I have also used the native tool in 8.0.1.
As far as I can tell, I need to do the following:
1. Take a local copy of the buddy list database (vpuserinfo.nsf) from ST651
2. Run the sandbox utility to convert all names to LDAP format
3. Edit the ACL to add the new server as manager
4. Copy the modified vpuserinfo.nsf to the ST801 server
5. Replace the design of vpuserinfo.nsf with the new template
6. Run the upgrade_util.cmd to update privacy information to the new format
7. Start the ST801 server
8. Log in and see my buddy list
Unfortunately this process is not working, it doesn't seem to matter in which order I attempt these steps the outcome is always failure.
The results tend to be one of the following:
1. Being able to log on, but see all my buddy list entries from the old server as not logged on, I can re-add them, and they show up as additional entries
2. Getting an RRV bucket is corrupt when trying to perform operations on VPUserinfo.nsf
3. Sametime server is unavalable - and I see this every minute in the console "Process D:\Lotus\Domino\nNOTESMM.EXE (5080/0x13D8) has terminated abnormally"
I know I wont see any users logged on on the ST651 server (they are after all different communities), but I am using two test a/cs to log on to both communities so I would expect this to work, and see two logged on users.
I have also tried the namechange utility in 8.0.1 and firstly I can tell you the documentation is risible. There are so many contradictions I am amazed it made it through quality control. Moreover, the tool doesn't seem to work.
The output is as follows:
D:\Lotus\Domino>stnamechange.cmd
D:\Lotus\Domino>jvm\bin\java.exe -cp StCore.jar;stnamechange.jar com.ibm.sametim
e.namechange.ChangeManager
Name Change Application version 8.0.1
Trace: Thu Oct 02 09:55:40 BST 2008 Main: got [0] arguments
Trace: Thu Oct 02 09:55:40 BST 2008 Creating config without parameters
Information: Thu Oct 02 09:55:40 BST 2008 Reading configuration from .\sametime.
ini
Information: Thu Oct 02 09:55:40 BST 2008 Configuration read...
Information: Thu Oct 02 09:55:40 BST 2008 TraceOn false
Information: Thu Oct 02 09:55:40 BST 2008 DbDirectory ./data
Information: Thu Oct 02 09:55:40 BST 2008 DebugLevel 2
D:\Lotus\Domino>
It takes a mere half second to dump this output to the screen, whereas the sandbox takes 10 minutes to complete its processing against the same buddy list database.
A sample of the log output from the sandbox tool is as follows:
Return to top
How to Migrate the Buddy List (~Lorraine Chuve... 2.Oct.08)
. . 
Print this page
